This chapter describes Thin Server Disk Task (TSDK) messages. For information on message content and how to use the message, refer to the Introduction.
| TSDK.001 |
Level: U-INFO
Short Syntax: TSDK.001 Deleting Host File: host_file_name (StagedFile: cached_file_name, DiskInfo: disk_info_file_name)
Long Syntax: TSDK.001 Deleting Host File: host_file_name (StagedFile: cached_file_name, DiskInfo: disk_info_file_name)
Description: This message is generated when a cached file is deleted from the disk drive.
| TSDK.002 |
Level: UI-ERROR
Short Syntax: TSDK.002 Couldn't schedule request_type of request_name file ( file_name), rc: return_code( rc)
Long Syntax: TSDK.002 Couldn't schedule request_type of request_name file ( file_name), rc: return_code( rc)
Description: This message is an internal error generated when the Disk Task is unable to perform a file request.
| TSDK.003 |
Level: UE-ERROR
Short Syntax: TSDK.003 An error occured while reading file_name
Long Syntax: TSDK.003 An error occured while reading file_name
Description: This message is generated if the Disk Task is unable to read a file from the hard file.
Cause: Corrupted hard file
Action: Restart the Thin Server Feature. If the error persists, restore the hard file.
| TSDK.004 |
Level: UI-ERROR
Short Syntax: TSDK.004 Mismatch between actual file size (of file_size) and expected file size (of file_size)
Long Syntax: TSDK.004 Mismatch between actual file size (of file_size) and expected file size (of file_size)
Description: This message is generated if the files stored on the hard file are inconsistant.
Cause: Corrupted hard file
Action: Restart the Thin Server Feature. If the error persists, restore the hard file.
| TSDK.005 |
Level: U-INFO
Short Syntax: TSDK.005 Owner of file_name isn't a configured Master File Server
Long Syntax: TSDK.005 Owner of file_name isn't a configured Master File Server
Description: This message is generated if the configuration is changed between NFS and RFS/400. All existing cached files will be deleted.
| TSDK.006 |
Level: C-INFO
Short Syntax: TSDK.006 Found file: directory/ file_name extension
Long Syntax: TSDK.006 Found file: directory/ file_name extension
Description: This message is generated while the Thin Server is initializing. It is generated for each file found on the hard file. The file names specified are the actual names of the files on the Thin Server's hard file (these names can be found in the first column of the Talk 5 List Cached-Files output).
| TSDK.007 |
Level: C-INFO
Short Syntax: TSDK.007 Adding: cached_file_name ( host_file_name) to cache
Long Syntax: TSDK.007 Adding: cached_file_name ( host_file_name) to cache
Description: This message is generated to indicate that a file stored on the hard file has been added to the set of files actually available to be served.
| TSDK.008 |
Level: U-TRACE
Short Syntax: TSDK.008 activate_or_terminate disk task
Long Syntax: TSDK.008 activate_or_terminate disk task
Description: This message indicates when the Thin Server disk task is starting or ending.
| TSDK.009 |
Level: ALWAYS
Short Syntax: TSDK.009 Update Finished: host_file_name, InTable: in_table_state( value)
Long Syntax: TSDK.009 Update Finished: host_file_name, InTable: in_table_state( value)
Description: This message is generated when a cached file update is complete. InTable indicates whether the file is still being cached.
| TSDK.010 |
Level: C-INFO
Short Syntax: TSDK.010 Creating File Does Not Exist entry for host_file_name
Long Syntax: TSDK.010 Creating File Does Not Exist entry for host_file_name
Description: This message is generated when an entry is created for a file which does not exist on the Master File Server.
| TSDK.011 |
Level: UI-ERROR
Short Syntax: TSDK.011 function returning error_code because reason
Long Syntax: TSDK.011 function returning error_code because reason
Description: This internal error is generated when the Disk Task is unable to process a request.
Cause: Couldn't Allocate A Request
Action: The Thin Server Feature ran out of memory while processing requests. Re-start any failed clients. If error persists reduce the number of clients accessing files simultaneously.
| TSDK.012 |
Level: UI-ERROR
Short Syntax: TSDK.012 function returning error_code
Long Syntax: TSDK.012 function returning error_code
Description: This message is generated if a Disk Task function fails.
| TSDK.013 |
Level: C-INFO
Short Syntax: TSDK.013 Create entry file_name
Long Syntax: TSDK.013 Create entry file_name
Description: This message is generated when a new file is added to the cached files on disk.
| TSDK.014 |
Level: C-TRACE
Short Syntax: TSDK.014 Create Files for host_file_name ( file_number), rc: return_code_description( return_code)
Long Syntax: TSDK.014 Create Files for host_file_name ( file_number), rc: return_code_description( return_code)
Description: This message is generated when a new file is added to the cached files on disk. The hex file_number relates to the actual file name on the hard file (as shown in the first column of the Talk 5 List Cached-Files output).
| TSDK.015 |
Level: UE-ERROR
Short Syntax: TSDK.015 Couldn't create_or_access Thin Server File Cache Directory ( directory) because reason
Long Syntax: TSDK.015 Couldn't create_or_access Thin Server File Cache Directory ( directory) because reason
Description: This message is generated when the Thin Server Feature is unable to create or access the cached files directory for some reason. If this occurs, there is some incompatibility with how the hard file has been used and use of the Thin Server Feature. Another possibility is that the hard file has become corrupted.
| TSDK.016 |
Level: U-INFO
Short Syntax: TSDK.016 Attempting to create Thin Server Directory: directory_name
Long Syntax: TSDK.016 Attempting to create Thin Server Directory: directory_name
Description: This message is generated to indicate that Disk Task is creating the sub-directory used to store cached files on the hard file.
| TSDK.017 |
Level: U-INFO
Short Syntax: TSDK.017 Thin Server Directory Created Successfully
Long Syntax: TSDK.017 Thin Server Directory Created Successfully
Description: This message is generated to indicate that Disk Task is creation of the sub-directory used to store cached files on the hard file succeeded.
| TSDK.018 |
Level: U-INFO
Short Syntax: TSDK.018 Thin Server File Cache Directory Was Empty
Long Syntax: TSDK.018 Thin Server File Cache Directory Was Empty
Description: This message is generated when there are no cached files when the Thin Server Feature starts.
| TSDK.019 |
Level: UE-ERROR
Short Syntax: TSDK.019 The following entry is a duplicate
Long Syntax: TSDK.019 The following entry is a duplicate
Description: This message is generated to indicate that a duplicate file was found in the Thin Server cache. A TSDK.1 message will also be generated indicating that the older file was deleted.
| TSDK.020 |
Level: UE-ERROR
Short Syntax: TSDK.020 Read-Only file found: file_name
Long Syntax: TSDK.020 Read-Only file found: file_name
Description: This message is generated when a read-only file is found on the hard file in the Thin Server directory. This should never happen and indicates corruption of the hard file.
| TSDK.021 |
Level: UI-ERROR
Short Syntax: TSDK.021 Internal Error: part_1 part_2( number)
Long Syntax: TSDK.021 Internal Error: part_1 part_2( number)
Description: This message is generated when a fatal internal error occurs in the Thin Server Disk Task.
| TSDK.022 |
Level: UE-ERROR
Short Syntax: TSDK.022 Abort on: file_name, LastByteAvail: bytes, FileSize: bytes
Long Syntax: TSDK.022 Abort on: file_name, LastByteAvail: bytes, FileSize: bytes
Description: This message is generated if a file update is interrupted (such as by loss of the connection to the Master File Server.
| TSDK.023 |
Level: UI-ERROR
Short Syntax: TSDK.023 Err in obj dtor: specific_error_message
Long Syntax: TSDK.023 Error in object destructor: specific_error_message
Description: This message is generated if an object destructor detects some invalid condition.
| TSDK.024 |
Level: C-TRACE
Short Syntax: TSDK.024 TRC: trace_message
Long Syntax: TSDK.024 TRACE: trace_message
Description: This message is generated when Disk Task internal traces are used.
| TSDK.025 |
Level: U-INFO
Short Syntax: TSDK.025 Rmv file_name (not in preload)
Long Syntax: TSDK.025 Remove file_name (not in preload list or include directories)
Description: This message is generated when Disk Task removes a file from the cache because it is no longer in the pre-load list or include directories.
| TSDK.026 |
Level: ALWAYS
Short Syntax: TSDK.026 Refresh protocol files starting_or_finished
Long Syntax: TSDK.026 Refresh protocol files starting_or_finished
Description: This message is generated when a refresh of the files belonging to a particular protocol is starting or completing. It may indicate that the refresh was aborted for some reason. If this occurs, the appropriate client messages should be observed (TSNC for NFS, TSRC for RFS/400).
| TSDK.027 |
Level: UI-ERROR
Short Syntax: TSDK.027 Unexpected RC from routine is error( number) optional_info
Long Syntax: TSDK.027 Unexpected RC from routine is error( number) optional_info
Description: This message is generated when any Disk Task function will return an unexpected return code
| TSDK.028 |
Level: C-TRACE
Short Syntax: TSDK.028 Acceptable RC from routine is error( number) optional_info
Long Syntax: TSDK.028 Acceptable RC from routine is error( number) optional_info
Description: This message is generated when Disk Task returns one of the following returns codes:
Cause: TSDK_NO_SAME_VERSION
Action: The NFS or RFS/400 client was checking if a file needs updating and the cached file as the same version as on the master file server.
Cause: TSDK_NO_NOT_ON_DISK
Action: The TFTP, NFS, or RFS/400 servers were attempting to access a file which is in the pre-load list, but not currently on the hard file.
Cause: TSDK_NO_NOT_AVAILABLE
Action: The TFTP, NFS, or RFS/400 servers were attempting to access a file which is not in the pre-load list.
Cause: TSDK_NO_NODE_NOT_FOUND
Action: The NFS server is attempting to access a file which is not in the cache.
| TSDK.029 |
Level: UE-ERROR
Short Syntax: TSDK.029 RAM memory cache was configured for configured_memoryk, using actual_memoryk
Long Syntax: TSDK.029 RAM memory cache was configured for configured_memoryk, using actual_memoryk
Description: This message is generated when the Thin Server feature was not able to use the configured amount of RAM memory cache.
Cause: The amount of memory to use for RAM cache may have been changed and the Thin Server Feature restarted without restarting the whole router.
Cause: More memory has been configured for the RAM cache than available in the router.
| TSDK.030 |
Level: UI-ERROR
Short Syntax: TSDK.030 Invalid Handle, Task: task_name(0x task_id), Handle: 0x handle, rc: error( error_number)
Long Syntax: TSDK.030 Invalid Handle, Task: task_name(0x task_id), Handle: 0x handle, rc: error( error_number)
Description: This message is generated any time Disk Task is passed an invalid handle.
| TSDK.031 |
Level: UE-ERROR
Short Syntax: TSDK.031 Aborting Disk Requests for host_file_name (FileState: file_state)
Long Syntax: TSDK.031 Aborting Disk Requests for host_file_name (FileState: file_state)
Description: This message is generated if a Refresh, Delete File, Flush, or verification of file version with the Master Server results in a file being deleted while being accessed. This may also happen when the Thin Server feature is Disabled or Restarted.
| TSDK.032 |
Level: CE-ERROR
Short Syntax: TSDK.032 Canceling_or_Aborting all Disk Requests for handle: task, 0x handle
Long Syntax: TSDK.032 Canceling_or_Aborting all Disk Requests for handle: task, 0x handle
Description: This message is generated when a Refresh, Delete File, Flush, or verification of file version with the Master Server results in a file being deleted while being accessed. This may also happen when the Thin Server feature is Disabled or Restarted.
| TSDK.033 |
Level: UE-ERROR
Short Syntax: TSDK.033 No room cache_or_hard_file for host_file_name
Long Syntax: TSDK.033 No room cache_or_hard_file for host_file_name
Description: This message is generated when a file is unable to be stored on the Thin Server because there is no more room.
Cause: RAM only mode (no hard file configured)
Action: Make sure the MEMORY-CACHE is SET to a value somewhat larger than the total space used by all the files to be cached.
Cause: Hard File Configured
Action: Make sure the hard file is operational and being used (check the configuration in Talk 5 for example). If the hard file is being used, make sure there are not too many files being downloaded.
| TSDK.034 |
Level: ALWAYS
Short Syntax: TSDK.034 Thin Server running without hard file because problem
Long Syntax: TSDK.034 Thin Server running without hard file because problem
Description: This message is generated if some problem causes the thin server to be unable to use the hard file.
Cause: General Problem
Action: Verify that the hard file is not corrupted and that there are not invalid files in the "TS" and "TS/DIR" directories. All files in these directories should be of the form "xxxxxxxx.INF" or "xxxxxxxx.DAT", where "xxxxxxxx" is a hexadecimal number. The files should also all be read-write.
Cause: Hardfile Not Useable
Action: Make sure a hard file is present. If one is, make sure there is enough free space on it.
Cause: Couldn't create Thin Server Directory
Action: Make sure there is space on the hard file, and that either the file "TS" doesn't exist, or if so, it is a directory. Also make sure that "TS/DIR" is either a directory, or non-existant.
Cause: Couldn't access Thin Server Directory
Action: Make sure there is a directory "TS" on the hard file. Also make sure that "TS/DIR" is a directory.